<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    
  </head>

  <body>
  <div>
    
    <div ng-include="headerInclude"></div>
    <div ng-controller="Apiman.ApiOverviewController" class="page container-pf-nav-pf-vertical container-fluid" data-field="page" ng-cloak="" ng-show="pageState == 'loaded'">
      <div ng-include="'plugins/api-manager/html/api/api_bc.include'"></div>
      <!-- Entity Summary Row -->
      <div ng-include="'plugins/api-manager/html/api/api_entity.include'"></div>

      <!-- Navigation + Content Row -->
      <div class="row">
        <!-- Left hand nav -->
        <div ng-include="'plugins/api-manager/html/api/api_tabs.include'"></div>
        <!-- /Left hand nav -->

        <!-- Content -->
        <div class="col-md-10 apiman-entity-content apiman-entity-overview">
          <!-- Content Summary -->
          <div class="col-md-12">
            <h1 apiman-i18n-key="api-details">API Details</h1>
            <p apiman-i18n-key="api-overview.api-description">
              Use the API details to modify the metadata, plans and policies for the API. There is no need to follow the
              tabs in order, but you will need to fill out a minimum amount of data before the API can be published to
              the gateway. In particular, the <strong>Implementation</strong> and <strong>Plans</strong> tabs are important.
            </p>

            <h2><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/impl" apiman-i18n-key="impl">Implementation</a></h2>
            <p apiman-i18n-key="api-overview.impl-description">
              The <strong>Implementation</strong> tab is where you go to configure the details of the real API being managed. This is
              where you tell the gateway where the API is, so that we can actually invoke it at runtime.
            </p>

            <h2><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/def" apiman-i18n-key="definition">Definition</a></h2>
            <p apiman-i18n-key="api-overview.definition-description">
              The <strong>Definition</strong> tab allows you to configure an optional API definition document for your API. An API
              definition is a detailed description of the capabilities of your API (operation names, http verbs, data
              models). You can add a Swagger spec document as your API definition.
            </p>

            <h2><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/plans" apiman-i18n-key="plans">Plans</a></h2>
            <p apiman-i18n-key="api-overview.plans-description">
              The <strong>Plans</strong> tab is used to configure which plans (defined in the organization) are available when a client
              wishes to create an API contract with this API. Optionally, an API can also be marked as Public. In that
              case, no API contract is required and the API can be invoked without sending an API Key.
            </p>

            <h2><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/policies" apiman-i18n-key="policies">Policies</a></h2>
            <p apiman-i18n-key="api-overview.policies-description">
              The <strong>Policies</strong> tab is where API-level policies can be configured. These policies will be enforced for all
              requests to the API, regardless of which user, Client App, or plan is being used.
            </p>

            <h2 apiman-status="Ready,Created,Retired" apiman-i18n-key="contracts">Contracts</h2>
            <h2 apiman-status="Published"><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/contracts" apiman-i18n-key="contracts">Contracts</a></h2>
            <p apiman-i18n-key="api-overview.contracts-description">
              The <strong>Contracts</strong> tab shows all of the registered consumers of the API. If the API is marked as Public, this
              tab will likely be empty.
            </p>

            <h2 apiman-status="Ready,Created,Retired" apiman-i18n-key="endpoint">Endpoint</h2>
            <h2 apiman-status="Published"><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/endpoint" apiman-i18n-key="endpoint">Endpoint</a></h2>
            <p apiman-i18n-key="api-overview.endpoint-description">
              The <strong>Endpoint</strong> tab will show you information about how to invoke the API once it is published to the API
              gateway.
            </p>

            <h2 ng-show="showMetrics" apiman-status="Ready,Created,Retired" apiman-i18n-key="metrics">Metrics</h2>
            <h2 ng-show="showMetrics" apiman-status="Published"><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/metrics" apiman-i18n-key="metrics">Metrics</a></h2>
            <p apiman-i18n-key="api-overview.metrics-description">
              The <strong>Metrics</strong> tab contains basic analytic information for the API. Use this tab to monitor the usage of the API.
            </p>

            <h2><a href="{{ pluginName }}/orgs/{{ api.organization.id }}/apis/{{ api.id }}/{{ version.version }}/activity" apiman-i18n-key="activity">Change Log</a></h2>
            <p apiman-i18n-key="api-overview.activity-description">
              The <strong>Change Log</strong> tab shows a history of all the changes made to the API. Essentially this is an audit log.
            </p>
            
          </div>
          <!-- /Content Summary -->
          
        </div>
        <!-- /Content -->
      </div>
    </div> <!-- /container-pf-nav-pf-vertical container-fluid -->
  </div>
  </body>
</html>
